Vehicle Immobilizing Devices, Systems, and Methods

ABSTRACT

A vehicle immobilizing device includes a lock, a user interface, memory configured to store an unlock code, and a processor. The lock has a latch mechanism and the processor controls movement of the latch mechanism from a locked position to an unlocked position so that the immobilizing device can be removed from a vehicle. A person installing the immobilizing device on a vehicle utilizes the user interface to enter and store an unlock code and an identification code in the device memory at the time of installation. Upon payment of an outstanding fine, a vehicle owner is provided with an unlock code. To remove the device from the vehicle the owner utilizes the user interface to enter unlock code and the processor causes the latch mechanism to move to the unlocked position upon determining that the unlock code input via the user interface matches an unlock code stored in the memory.

RELATED APPLICATION

This application is a continuation application of pending U.S. patentapplication Ser. No. 13/408,342, filed Feb. 29, 2012, the disclosure ofwhich is incorporated herein by reference as if set forth in itsentirety.

FIELD OF THE INVENTION

The present invention relates generally to vehicles and, moreparticularly, to devices, systems and methods for temporarilyimmobilizing vehicles.

BACKGROUND

Vehicle parking laws are typically enforced by issuing a summons andplacing the summons on a vehicle in violation. Typically, the vehicleowner is required to pay the fine or appear in court to contest thesummons. Unfortunately, in many areas, some vehicle owners do notpromptly pay fines that are due and allow summons and fines toaccumulate.

One solution to insure payment of such fines is to place an immobilizingdevice, often referred to as a clamp or “boot”, on the wheel of avehicle currently in violation and/or on the wheel of a vehicle of ascofflaw with unpaid parking summons. A conventional wheel boottypically consists of a clamp that surrounds a vehicle wheel, and isdesigned to prevent removal of both itself and the wheel. A conventionalvehicle wheel boot 10 is illustrated in FIGS. 1 and 2. The illustratedwheel boot 10 includes a base 14 and a pair of clamping members 16, 18extending from the base 14. Clamping member 18 includes a wheelengagement dome 20 that is configured to engage an outer portion of awheel 12 (FIG. 2). The clamping members 16, 18 are movable relative toeach other from an open position wherein a vehicle wheel 12 can beinserted between the clamping members 16, 18 to a closed positionwherein the clamping members engage the vehicle wheel 12 to prevent thewheel boot 10 from being removed from the vehicle wheel 12. A latchmechanism (not illustrated) locks the clamping members in the closedposition. When attached to a wheel of a vehicle, operation of thevehicle is virtually impossible since the wheel is no longer able toroll due to the presence of the wheel boot 10. Other conventionalimmobilizing devices are described in Japanese Patent No. JP 58076348,UK Patent Nos. 3008370 and 3007353, and U.S. Pat. Nos. 1,489,272;1,530,622; 3,907,072; 4,768,359; 5,134,868; 5,315,848; 5,372,018;5,829,285; and 5,673,574, the disclosures of which are incorporatedherein by reference in their entireties.

The use of immobilizing devices, such as illustrated in FIGS. 1-2, hasbecome popular with law enforcement, parking attendants, municipalgovernments, and the like in the enforcement of parking and otherviolations. In use, an installer places an immobilizing device on avehicle wheel, thereby immobilizing the vehicle. Upon returning to thevehicle, the offender is prompted by a notice placed on the vehicle(e.g., a sticker on the window, notice under a windshield wiper, etc.)to call the appropriate entity, e.g., the police, parking authority, orother third party, in order to learn how to have the immobilizing deviceremoved. The offender is prompted during the call to make his/her way tothe police station, parking authority, or other third party location.Typically, the offender is required to pay the fine for a currentviolation and any other outstanding fines. Once the offender has paidall outstanding amounts, the appropriate entity typically sends someoneto remove the immobilizing device from the vehicle.

Some conventional immobilizing devices may have a combination lock asdescribed, for example, in U.S. Pat. No. 5,829,285, which isincorporated herein by reference in its entirety. As such, once theoffender has paid all outstanding amounts, he/she may be given a codefor unlocking the immobilizing device. Typically, the person is requiredto pay a deposit and then return the immobilizing device to a specifiedlocation in order to receive a refund of the deposit. Unfortunately, theprocess of contacting a responsible agency, paying a fine, and obtainingan unlocking code or combination can be time consuming and frustratingto vehicle owners.

SUMMARY

It should be appreciated that this Summary is provided to introduce aselection of concepts in a simplified form, the concepts being furtherdescribed below in the Detailed Description. This Summary is notintended to identify key features or essential features of thisdisclosure, nor is it intended to limit the scope of the invention.

According to some embodiments of the present invention, a vehicleimmobilizing device includes a lock that locks the immobilizing devicewhen installed on a vehicle and prevents unauthorized removal of theimmobilizing device from the vehicle. The immobilizing device alsoincludes a user interface, a memory configured to store an unlock code,and a processor that is in communication with the user interface andmemory. The lock has a latch mechanism that is movable between lockedand unlocked positions. The processor controls movement of the latchmechanism from the locked position to the unlocked position so that theimmobilizing device can be removed from a vehicle upon determining thatan unlock code input via the user interface matches an unlock codestored in the device memory.

The user interface allows a user to communicate with the processor andincludes a keypad and display. For example, in some embodiments of thepresent invention, a person installing the immobilizing device on avehicle utilizes the user interface to enter and store an unlock code inthe device memory. Alternatively, the installer utilizes the userinterface to cause the device processor to generate an unlock code andstore the generated code in the device memory.

A vehicle owner desiring to remove the immobilizing device from his/hervehicle utilizes the user interface to enter removal authorizationinformation which may cause the processor to display an unlock code.Removal authorization information may include financial paymentinformation and/or verification that payment has been made for anyoutstanding debts, fines, etc. For example, a vehicle owner inputs acode that represents that all outstanding debts/fines have been paid. Inresponse, an unlock code is displayed to the vehicle owner via the userinterface. The vehicle owner then enters the displayed unlock code viathe keypad of the user interface. In response, the device processorcauses the latch mechanism to be moved from a locked position to anunlocked position so that the vehicle immobilizing device can be removedfrom the vehicle.

In other embodiments of the present invention, the processor of animmobilizing device is configured to wirelessly receive an unlock codefrom a remote source and store the unlock code in memory when theimmobilizing device is installed on a vehicle. Such a remote source maybe a device geographically remote from the vehicle immobilizing device,such as a server or other computing device. Such a remote source mayalso include a mobile device carried by an installer of the immobilizingdevice, or located in a vehicle of an installer.

In some embodiments of the present invention, an immobilizing deviceprocessor is configured to generate a unique unlock code and anidentification code for the immobilizing device and store the generatedcodes in the device memory when the immobilizing device is installed ona vehicle. The processor may generate unlock codes and identificationcodes in various ways. For example, in some embodiments, an immobilizingdevice may include a clock and the processor uses time and/or dateinformation from the clock to generate a unique unlock code andidentification code. In other embodiments, the vehicle immobilizingdevice may include an environmental sensor that is configured to obtainenvironmental condition information (e.g., temperature, humidity, windspeed, ozone levels, etc.) in a vicinity of the immobilizing device. Theprocessor uses environmental condition information obtained from thesensor to generate a unique unlock code and identification code. Inother embodiments, the immobilizing device may include a GlobalPositioning System (GPS) receiver. The processor uses locationinformation obtained from the GPS device to generate a unique unlockcode and identification code.

A vehicle immobilizing device, according to some embodiments of thepresent invention, may include a transceiver that is configured towirelessly communicate with other devices and/or communications systems.For example, in some embodiments, the processor is configured to receivefinancial payment information from a user (e.g., regarding a currentfine and/or past due fines and/or other violations), report thefinancial payment information to a transaction approval service via thetransceiver, receive transaction approval or denial from the transactionapproval service via the transceiver, and display an unlock code storedin memory via the display in response to receiving transaction approval.Alternatively, in response to receiving transaction approval, theprocessor may be configured to cause the latch mechanism to be movedfrom a locked position to an unlocked position without displaying anunlock code and without requiring the vehicle owner to enter an unlockcode.

In some embodiments, financial payment information may be input by auser via the user interface, for example, via a keypad associated withthe user interface. In other embodiments, a vehicle immobilizing devicemay include a slot for receiving a payment card and a magnetic stripereader associated with the slot. The processor is configured to receivefinancial payment information from a magnetic stripe of a payment cardvia the magnetic stripe reader.

In other embodiments, a vehicle immobilizing device may include a nearfield communication (NFC) reader. The processor is configured to receivepayment information from an NFC tag placed in proximity with the nearfield communication reader by a user.

In other embodiments, a vehicle immobilizing device may include aradio-frequency identification (RFID) reader. The processor isconfigured to receive payment information from an RFID tag placed inproximity with the RFID reader by a user.

According to other embodiments of the present invention, a vehicleimmobilizing device may not have a user interface. Instead, theimmobilizing device processor is configured to receive an unlock codefrom a remote source and move the latch mechanism from the lockedposition to the unlocked position so that the vehicle immobilizingdevice can be removed from a vehicle when the received unlock codematches an unlock code stored in memory, for example, in response to avehicle owner providing financial payment to a parking authority orother third party.

According to some embodiments of the present invention, a systemutilized by a parking authority or other third party includes aplurality of vehicle immobilizing devices, and a server that isconfigured to wirelessly communicate with each of the immobilizingdevices. The server is configured to generate a unique unlock code andidentification code for a respective immobilizing device when theimmobilizing device is installed on a vehicle. The server stores thegenerated unlock code and identification code, and wirelessly transmitsthe unlock code and identification code to the respective immobilizingdevice processor for storage in the immobilizing device memory.

The server may generate an unlock code and/or an identification code fora respective vehicle immobilizing device in various ways. For example,in some embodiments of the present invention, the server generates anunlock code and/or an identification code for a respective vehicleimmobilizing device via a random number generator. The random numbergenerator may be associated with the server, with the immobilizingdevice, or may be associated with another device geographically remotefrom the server that the server communicates with.

In other embodiments, an immobilizing device includes a clock and theserver generates an unlock code and/or an identification code for arespective vehicle immobilizing device using time and/or dateinformation from the clock. In other embodiments, the server includes aclock and the server generates an unlock code and/or an identificationcode for a respective vehicle immobilizing device using time and/or dateinformation from the clock.

In other embodiments, a vehicle immobilizing device includes anenvironmental sensor that is configured to obtain environmentalcondition information (e.g., temperature, humidity, wind speed, ozonelevels, etc.) in a vicinity of the vehicle immobilizing device. Theserver uses environmental condition information obtained from the sensorto generate an unlock code and/or an identification code for the vehicleimmobilizing device. In other embodiments, a vehicle immobilizing devicemay include a GPS receiver. The server uses location informationobtained from the GPS receiver to generate an unlock code and/or anidentification code for the vehicle immobilizing device.

In some embodiments of the present invention, a mobile code generationdevice may be utilized by an installer to generate an unlock code and anidentification code for an immobilizing device when the immobilizingdevice is installed on a vehicle. The code generation device wirelesslycommunicates with the vehicle immobilizing device and with a remoteserver. The code generation device generates an unlock code and anidentification code and transmits the generated unlock code andidentification code to the server for storage. The code generationdevice also transmits the unlock code to the respective immobilizingdevice processor for storage in memory.

The code generation device may generate an unlock code and/or anidentification code for a respective vehicle immobilizing device invarious ways. For example, in some embodiments of the present invention,the code generation device generates an unlock code and/or anidentification code for a respective vehicle immobilizing device via arandom number generator. The random number generator may be associatedwith the code generation device, with the immobilizing device, with theserver, or may be associated with another device geographically remotefrom the code generation device that the code generation devicecommunicates with.

In other embodiments, an immobilizing device includes a clock and thecode generation device generates an unlock code and/or an identificationcode for a respective vehicle immobilizing device using time and/or dateinformation from the clock. In other embodiments, the code generationdevice includes a clock and the code generation device generates anunlock code and/or an identification code for a respective vehicleimmobilizing device using time and/or date information from the clock.

In other embodiments, a vehicle immobilizing device includes anenvironmental sensor that is configured to obtain environmentalcondition information (e.g., temperature, humidity, wind speed, ozonelevels, etc.) in a vicinity of the vehicle immobilizing device. The codegeneration device uses environmental condition information obtained fromthe sensor to generate an unlock code and/or an identification code forthe vehicle immobilizing device. In other embodiments, a vehicleimmobilizing device or the code generation device may include a GPSreceiver. The code generation device uses location information obtainedfrom the GPS receiver to generate an unlock code and/or anidentification code for the vehicle immobilizing device.

Each vehicle immobilizing device processor is configured to receiveremoval authorization information input via a respective user interfaceby a user and display an unlock code stored in memory via the display inresponse to receiving the removal authorization information. In someembodiments, a vehicle immobilizing device processor may be configuredto receive removal authorization information input via a respective userinterface by a user and cause a respective latch mechanism to be movedfrom a locked position to an unlocked position so that the vehicleimmobilizing device can be removed from a vehicle.

In some embodiments of the present invention, one or more of theimmobilizing devices may include a transceiver that is configured towirelessly communicate with other devices and/or communications systems.For example, in some embodiments, an immobilizing device processor isconfigured to receive financial payment information from a user, reportthe financial payment information to a transaction approval service viathe transceiver, receive transaction approval or denial from thetransaction approval service via the transceiver, and display an unlockcode stored in memory via the display in response to receivingtransaction approval. Alternatively, in response to receivingtransaction approval, an immobilizing device processor may be configuredto cause a latch mechanism to move from a locked position to an unlockedposition without displaying an unlock code.

In other embodiments of the present invention, the server is configuredto send a command to an immobilizing device processor to cause theimmobilizing device processor to move the latch mechanism from thelocked position to the unlocked position so that the respective vehicleimmobilizing device can be removed from a vehicle.

As described above, in some embodiments of the present invention,financial payment information may be input by a user via a userinterface of an immobilizing device. In other embodiments, animmobilizing device may include a slot for receiving a payment card anda magnetic stripe reader associated with the slot. The immobilizingdevice processor is configured to receive financial payment informationfrom a magnetic stripe of a payment card via the magnetic stripe reader.In other embodiments, an immobilizing device may include an NFC readeror an RFID reader. The processor is configured to receive paymentinformation from an NFC tag/RFID tag placed in proximity with the NFCreader/RFID reader by a user.

According to other embodiments of the present invention, a systemutilized by, for example, a parking authority includes a plurality ofvehicle immobilizing devices, and a server configured to wirelesslycommunicate with the vehicle immobilizing devices. The server isconfigured to generate an unlock code and an identification code for arespective vehicle immobilizing device when the vehicle immobilizingdevice is utilized to immobilize a vehicle (i.e., when the device isinstalled on a vehicle). The server stores the generated unlock code andidentification code, and transmits the unlock code to the respectivevehicle immobilizing device processor for storage in memory. Also, theserver is configured to send a command to a vehicle immobilizing deviceprocessor to cause the processor to move the respective latch mechanismfrom the locked position to the unlocked position so that the respectiveimmobilizing device can be removed from a vehicle.

According to some embodiments of the present invention, a method ofimmobilizing a vehicle includes immobilizing the vehicle with animmobilizing device, generating an unlock code and an identificationcode for the vehicle immobilizing device, and storing the unlock code ina memory of the immobilizing device. In some embodiments, the generatedunlock code and identification code are also stored at a remotelocation. The immobilizing device includes a lock that includes a latchmechanism that is movable between locked and unlocked positions. Theprocessor is in communication with the memory and, controls movement ofthe latch mechanism from the locked position to the unlocked position.In some embodiments, the unlock code and identification code isgenerated by a mobile electronic device in communication with theimmobilizing device processor.

According to some embodiments of the present invention, a method ofreleasing an immobilizing device from a vehicle, wherein theimmobilizing device includes a lock having a latch mechanism that ismovable between locked and unlocked positions, includes receivingremoval authorization information input via a user interface of theimmobilizing device, and then displaying to a user an unlock code storedin a memory of the immobilizing device via the user interface inresponse to receiving the removal authorization information. Theimmobilizing device includes a processor that causes the latch mechanismto be moved from the locked position to the unlocked position inresponse to receiving user input of the unlock code via the userinterface.

According to other embodiments of the present invention, a method ofreleasing a vehicle immobilizing device from a vehicle, wherein thevehicle immobilizing device includes a lock having a latch mechanismthat is movable between locked and unlocked positions, includesreceiving removal authorization information input via a user interfaceof the immobilizing device, and causing the latch mechanism to be movedfrom a locked position to an unlocked position via a processor of theimmobilizing device so that the immobilizing device can be removed froma vehicle.

According to other embodiments of the present invention, a method ofreleasing an immobilizing device from a vehicle, wherein theimmobilizing device includes a lock having a latch mechanism that ismovable between locked and unlocked positions, includes receivingfinancial payment information from a user via a user interface of theimmobilizing device, reporting the financial payment information to atransaction approval service via a transceiver of the immobilizingdevice, receiving transaction approval from the transaction approvalservice via the transceiver, displaying an unlock code stored in memoryto the user via the user interface, and causing the latch mechanism tobe moved from the locked position to the unlocked position via aprocessor of the immobilizing device in response to receiving user inputof the unlock code via the user interface.

According to other embodiments of the present invention, a vehicleimmobilizing device includes a lock that prevents unauthorized removalof the immobilizing device from a vehicle, and a user interface. Thelock is configured to receive and store an unlock code duringinstallation of the immobilizing device on a vehicle. The user interfaceis utilized by an installer for providing the lock with an unlock code.The user interface is utilized for subsequently entering the unlock codeto unlock the lock in order to remove the immobilizing device from avehicle.

According to some embodiments of the present invention, a method ofimmobilizing a vehicle includes immobilizing the vehicle with animmobilizing device, generating an unlock code and an identificationcode for the vehicle immobilizing device, and storing the unlock code ina lock of the immobilizing device. In some embodiments, the generatedunlock code and identification code are also stored at a remotelocation.

It is noted that aspects of the invention described with respect to oneembodiment may be incorporated in a different embodiment although notspecifically described relative thereto. That is, all embodiments and/orfeatures of any embodiment can be combined in any way and/orcombination. Applicant reserves the right to change any originally filedclaim or file any new claim accordingly, including the right to be ableto amend any originally filed claim to depend from and/or incorporateany feature of any other claim although not originally claimed in thatmanner. These and other objects and/or aspects of the present inventionare explained in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which form a part of the specification,illustrate various embodiments of the present invention. The drawingsand description together serve to fully explain embodiments of thepresent invention.

FIG. 1 is a perspective view of a conventional vehicle wheel boot.

FIG. 2 illustrates the vehicle wheel boot of FIG. 1 attached to a wheelof a vehicle so as to immobilize the vehicle.

FIG. 3 is a block diagram that illustrates vehicle immobilizing devicesaccording to various embodiments of the present invention.

FIG. 4A is a perspective view of a vehicle immobilizing device,according to some embodiments of the present invention.

FIG. 4B is a partial elevation view of the vehicle immobilizing deviceof FIG. 4A illustrating a user interface for communicating with aninternal processor, according to some embodiments of the presentinvention.

FIG. 4C is a partial elevation view of the vehicle immobilizing deviceof FIG. 4A illustrating a user interface according to other embodimentsof the present invention.

FIG. 4D is a partial elevation view of the vehicle immobilizing deviceof FIG. 4A illustrating a user interface according to other embodimentsof the present invention.

FIG. 5A is a perspective view of a vehicle immobilizing device,according to some embodiments of the present invention.

FIG. 5B is a top plan view of the vehicle immobilizing device of FIG. 5Aengaging a vehicle wheel prior to being locked.

FIG. 5C is a top plan view of the vehicle immobilizing device of FIG. 5Aengaging a vehicle wheel and in a locked configuration.

FIG. 6 is a block diagram of a vehicle immobilizing device system,according to some embodiments of the present invention.

FIG. 7 is a block diagram that illustrates details of an exemplaryprocessor and memory that may be used to implement various functions ofa vehicle immobilizing device, according to some embodiments of thepresent invention.

FIG. 8 is a block diagram that illustrates details of an exemplaryprocessor and memory that may be used to implement various functions ofa server that is configured to communicate with a plurality of vehicleimmobilizing devices, according to some embodiments of the presentinvention.

FIG. 9 is a block diagram that illustrates details of an exemplaryprocessor and memory that may be used to implement various functions ofa a code generation device, according to some embodiments of the presentinvention.

DETAILED DESCRIPTION

The present invention will now be described more fully hereinafter withreference to the accompanying figures, in which embodiments of theinvention are shown. This invention may, however, be embodied in manydifferent forms and should not be construed as limited to theembodiments set forth herein. Like numbers refer to like elementsthroughout. In the figures, certain components or features may beexaggerated for clarity. In addition, the sequence of operations (orsteps) is not limited to the order presented in the claims unlessspecifically indicated otherwise.

It will be understood that when a feature or element is referred to asbeing “on” another feature or element, it can be directly on the otherfeature or element or intervening features and/or elements may also bepresent. In contrast, when a feature or element is referred to as being“directly on” another feature or element, there are no interveningfeatures or elements present. It will also be understood that, when afeature or element is referred to as being “connected”, “attached” or“coupled” to another feature or element, it can be directly connected,attached or coupled to the other feature or element or interveningfeatures or elements may be present. In contrast, when a feature orelement is referred to as being “directly connected”, “directlyattached” or “directly coupled” to another feature or element, there areno intervening features or elements present. Although described or shownwith respect to one embodiment and/or figure, the features and elementsso described or shown can apply to other embodiments and/or figures.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, steps, operations, elements, components, and/or groupsthereof. As used herein, the term “and/or” includes any and allcombinations of one or more of the associated listed items and may beabbreviated as “/”. As used herein, phrases such as “between X and Y”and “between about X and Y” should be interpreted to include X and Y. Asused herein, phrases such as “between about X and Y” mean “between aboutX and about Y.” As used herein, phrases such as “from about X to Y” mean“from about X to about Y.”

Spatially relative terms, such as “under”, “below”, “lower”, “over”,“upper” and the like, may be used herein for ease of description todescribe one element or feature's relationship to another element(s) orfeature(s) as illustrated in the Figures. It will be understood that thespatially relative terms are intended to encompass differentorientations of a device in use or operation in addition to theorientation depicted in the Figures. For example, if a device in theFigures is inverted, elements described as “under” or “beneath” otherelements or features would then be oriented “over” the other elements orfeatures. Thus, the exemplary term “under” can encompass both anorientation of over and under. The device may be otherwise oriented(rotated 90 degrees or at other orientations) and the spatially relativedescriptors used herein interpreted accordingly. Similarly, the terms“upwardly”, “downwardly”, “vertical”, “horizontal” and the like are usedherein for the purpose of explanation only unless specifically indicatedotherwise.

It will be understood that although the terms first and second are usedherein to describe various features or elements, these features orelements should not be limited by these terms. These terms are only usedto distinguish one feature or element from another feature or element.Thus, a first feature or element discussed below could be termed asecond feature or element, and similarly, a second feature or elementdiscussed below could be termed a first feature or element withoutdeparting from the teachings of the present invention.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which this invention belongs. It will befurther understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the specification andrelevant art and should not be interpreted in an idealized or overlyformal sense unless expressly so defined herein. Well-known functions orconstructions may not be described in detail for brevity and/or clarity.

The term “latch mechanism”, as used herein, refers to any type ofmechanical element, electromechanical element, or electronic elementassociated with a lock of a vehicle immobilizing device, which causesthe lock to be “locked” and “unlocked”. When a vehicle immobilizingdevice lock is locked, the immobilizing device is unremovable from avehicle. Conversely, when a vehicle immobilizing device lock isunlocked, the immobilizing device is removable from a vehicle.

Some embodiments of the present invention are directed to a “smart”vehicle immobilizing device that allows a person whose vehicle has beenfitted with such a device to make a payment of the amount that is owedvia the immobilizing device. A person whose vehicle has been immobilizedcan interact with the immobilizing device to find out how much is owedfor current and/or past due fines/debts and then pay the amount via, forexample, a credit card. The person is also given a code for unlockingthe device via a user interface associated with the immobilizing device.The user interface may also provide instructions to the person as towhere to return the immobilizing device.

In some embodiments of the present invention, the amount of a fine/debtthat is owed can be programmed into the immobilizing device by a personinstalling the immobilizing device on a vehicle. The amount of afine/debt owed can also be remotely programmed into the immobilizingdevice, for example, from the location of a police station, parkingauthority, or other third party, etc.

Referring now to FIG. 3, a vehicle immobilizing device 100, according tosome embodiments of the present invention is illustrated. Theimmobilizing device 100 includes a lock 102 configured to lock theimmobilizing device and prevent unauthorized removal of the immobilizingdevice from a vehicle. The lock 102 has a latch mechanism that ismovable between locked and unlocked positions. Various types of locksand latch mechanisms may be utilized in accordance with embodiments ofthe present invention, without limitation. An exemplaryelectromechanical locking mechanism that may be incorporated intoimmobilizing devices in accordance with embodiments of the presentinvention is described in U.S. Pat. No. 6,337,618, which is incorporatedherein by reference in its entirety. Exemplary electronic locks that maybe incorporated into immobilizing devices in accordance with embodimentsof the present invention are described in U.S. Pat. Nos. 8,093,986;7,193,503; and 5,894,277, which are incorporated herein by reference intheir entireties. However, embodiments of the present invention are notlimited to any particular type of lock or latch mechanism.

Still referring to FIG. 3, an immobilizing device 100 includes a memory106 that is configured to store an unlock code and a processor 104 thatis in communication with the device memory 106. The processor 104controls movement of the latch mechanism from the locked position to theunlocked position so that the immobilizing device 100 can be removedfrom a vehicle upon determining that an unlock code input via the userinterface 108 matches an unlock code stored in the memory 106, as willbe described in further detail below.

In some embodiments of the present invention, an immobilizing device 100includes a user interface 108. The device processor 104 is incommunication with the user interface 108 and is configured to displayinformation to a user via the user interface 108 and to receiveinformation input by a user via the user interface 108. An exemplaryuser interface 108 incorporated into an immobilizing device 100 isillustrated in FIGS. 4A-4B. The illustrated user interface 108 includesa keypad 109 and a display 111 (FIG. 4B) that allows a user tocommunicate with the processor 104. For example, in some embodiments ofthe present invention, a person installing an immobilizing device 100 ona vehicle utilizes the user interface 108 to enter and store an unlockcode in the immobilizing device memory 106, or utilizes the userinterface 108 to cause the processor 104 to generate an unlock code andstore the generated code in memory 106. The display 111 may be a LiquidCrystal Display (LCD) module, or any other low power consumption displaydevice. Various types of displays may be utilized in accordance withembodiments of the present invention, without limitation. Moreover,various types of user interfaces may be utilized in accordance withembodiments of the present invention, without limitation. Embodiments ofthe present invention are not limited to any particular type of userinterface.

A vehicle owner desiring to remove an immobilizing device 100 fromhis/her vehicle utilizes the user interface 108 to enter removalauthorization information which may cause the device processor 104 todisplay an unlock code. The user inputs the displayed unlock code viathe user interface 108, for example, via the keypad 109, to unlock theimmobilizing device 100. For example, in the illustrated embodiment,“AZ402” is displayed in the display of user interface 108, which mayrepresent an unlock code displayed by the processor 104 in response toremoval authorization information input by a vehicle owner. The vehicleowner can enter this unlock code via the keypad 109 to unlock theimmobilizing device 100.

Embodiments of the present invention are not limited to the userinterface 108 of FIGS. 4A and 4B. Various other types of user interfacesmay be utilized, without limitation. In some embodiments of the presentinvention, an immobilizing device 100 user interface may not include adisplay. For example, FIG. 4C illustrates an immobilizing device havinga dial 108 d as a user interface, and FIG. 4D illustrates animmobilizing device 100 having a keypad 108 k as a user interface.

In other embodiments of the present invention, the device processor 104may be configured to cause movement of the latch mechanism from a lockedposition to an unlocked position so that the vehicle immobilizing devicecan be removed from a vehicle in response to removal authorizationinformation being input via the user interface 108 by a user.

In some embodiments of the present invention, an immobilizing device 100may include a lock 102 that is configured to store an unlock codegenerated at the time of installation of the device by an installer. Aninstaller of the immobilizing device enters a unique unlock code (e.g.,the date when the immobilizing device 100 is installed on a vehicle,etc.) via a user interface (e.g., user interface 108, 108 d, 108 k). Thelock 102 is configured to remember the unlock code entered by theinstaller. The installer submits the entered unlock code along with anidentification code for the immobilizing device 100 to a third party(e.g., the police, a parking authority, a municipality, etc.). To unlockthe lock 102, a vehicle owner obtains the entered unlock code from thethird party (e.g., the police, a parking authority, a municipality,etc.) after paying any outstanding fines/debts and enters the unlockcode via the user interface (e.g., user interface 108, 108 d, 108 k).

Referring back to FIG. 3, according to some embodiments of the presentinvention, a vehicle immobilizing device 100 may include a clock 110.The clock 110 may facilitate the generation of an unlock code and/or anidentification code for an immobilizing device 100 at the time ofinstallation of the immobilizing device on a vehicle. For example, thedevice processor 104 may use time and/or date information from the clock110 to generate an unlock code, which is then stored in memory 106 andalso communicated to a remotely located server 200 (FIG. 6) of a parkingauthority or other third party, as described below. This allows for aunique unlock code and/or identification code to be generated in realtime and on the fly, thereby eliminating the need for pre-existing codesto be assigned for a particular immobilizing device.

According to some embodiments of the present invention, a vehicleimmobilizing device 100 may include a Global Positioning System (GPS)receiver 112. In addition to providing location information (e.g.,latitude and longitude information) for an immobilizing device (i.e.,where a vehicle is located on which the immobilizing device isinstalled), the GPS receiver 112 may facilitate the generation of anunlock code and/or an identification code for an immobilizing device 100at the time of installation of the immobilizing device on a vehicle. Forexample, the processor 104 may use location information from the GPSreceiver 112 to generate an unlock code, which is then stored in memory106 and also communicated to a remotely located server 200 (FIG. 6) of aparking authority or other third party, as described below. This allowsfor a unique unlock code and/or identification code to be generated inreal time and on the fly, thereby eliminating the need for pre-existingcodes to be assigned for a particular immobilizing device.

According to some embodiments of the present invention, a vehicleimmobilizing device 100 may include one or more environmental sensors114 configured to obtain environmental condition information in avicinity of the vehicle immobilizing device 100 when installed on avehicle. Exemplary environmental sensors that may be utilized inaccordance with embodiments of the present invention include, but arenot limited to, sensors configured to detect and/or measure one or moreof the following types of environmental information: humidity level,temperature, barometric pressure, ozone level, carbon monoxide level,carbon dioxide level, airborne pollution, wind speed and/or direction,noise pollution, etc. The processor 104 uses environmental conditioninformation obtained from the one or more environmental sensors 114 togenerate an unlock code, which is then stored in memory 106 and alsocommunicated to a remotely located server 200 (FIG. 6) of a parkingauthority or other third party, as described below. This allows for aunique unlock code and/or identification code to be generated in realtime and on the fly, thereby eliminating the need for pre-existing codesto be assigned for a particular immobilizing device.

According to some embodiments of the present invention, a vehicleimmobilizing device 100 may include a transceiver 116 (i.e., acombination transmitter/receiver) that is configured to wirelesslycommunicate with other devices and/or communications systems. Forexample, in some embodiments of the present invention, an immobilizingdevice processor 104 is configured to receive financial paymentinformation from a user, report the financial payment information to atransaction approval service via the transceiver 116, and receivetransaction approval or denial from the transaction approval service viathe transceiver 116. The device processor 104 displays an unlock codestored in memory 106 via the user interface 108 in response to receivingtransaction approval. The transceiver 116 is also utilized to transmitan unlock code and identification code generated by an immobilizingdevice processor 104 at the time of installation of the immobilizingdevice on a vehicle to a remotely located server 200 (FIG. 6) of aparking authority or other third party, as described below. In someembodiments of the present invention, the transceiver 116 is utilized toreceive an unlock code generated remotely by a server 200 (FIG. 6) of aparking authority or other third party, or by a code generation device400, as described below.

An immobilizing device 100, according to embodiments of the presentinvention, may communicate wirelessly via transceiver 116 with a remoteserver and/or other devices via RF communications, Bluetooth®communications, pulsed magnetic or electric fields, infrared signals orany other forms of wireless transmission.

According to some embodiments of the present invention, a vehicleimmobilizing device 100 may be configured to conduct financialtransactions with a user. For example, an immobilizing device 100 may beconfigured to receive financial payment information from a user, such asa vehicle owner, forward the financial payment information to atransaction approval service, and receive a response from thetransaction approval service, e.g., either transaction approval ordisapproval. In some embodiments, financial payment information may beinput by a user via the user interface 108 of an immobilizing device.For example, a user may enter a credit card number (or a debit cardnumber, etc.) via the keypad 109 (FIG. 4B) of user interface 108. Inother embodiments of the present invention, an immobilizing device 100may have a slot for receiving a payment card and a magnetic stripereader 118 associated with the slot. The device processor 104 isconfigured to receive financial payment information from a magneticstripe of a payment card via the magnetic stripe reader 118. Using thetransceiver 116, the processor 104 forwards financial paymentinformation obtained from a payment card via the magnetic stripe reader118 to a transaction approval service, and receives a response from thetransaction approval service, e.g., either transaction approval ordisapproval.

Immobilizing devices 100, according to embodiments of the presentinvention, may utilize any type of technology for receiving financialpayment information from users. For example, in some embodiments, avehicle immobilizing device 100 may include a near field communication(NFC) reader 120 that is configured to obtain information from an NFCtag placed in proximity therewith. NFC is a short-range wirelessconnectivity standard (Ecma-340, ISO/IEC 18092) that uses magnetic fieldinduction to enable communication between devices when they're touchedtogether, or brought within close proximity (e.g., a few centimeters,etc.) of each other.

In other embodiments of the present invention, a vehicle immobilizingdevice 100 may include a radio-frequency identification (RFID) reader122 that is configured to obtain information from an RFID tag placed inproximity therewith. An RFID tag is a specially designed electronic tag,which is typically implemented as the combination of a computer chip andan antenna, that is placed on, or embedded in, an object. RFID tags workin conjunction with an RFID reader, which typically includes atransceiver and an antenna. The RFID reader transmits a signal that maybe used to: (a) energize or “excite” an RFID tag, and (b) receive anddemodulate and/or decode information that is transmitted by theenergized RFID tag.

Embodiments of the present invention are not limited to any particulartype of vehicle immobilizing device 100. For example, conventional“wheel boot” immobilizing devices that are physically attached to avehicle wheel, such as illustrated in FIG. 4A may be modified to includevarious functions of the present invention illustrated in FIG. 3. Inaddition, immobilizing devices 100 that impede vehicle motion, but arenot physically attached to a vehicle, may also be utilized, such asillustrated in FIGS. 5A-5C, in various embodiments of the presentinvention. Conventional immobilizing devices described, for example, inU.S. Pat. Nos. 5,829,285; 5,333,477; 5,437,171; 6,032,497; 6,360,571;and 6,662,607, which are incorporated herein by reference in theirentireties, can be modified to include various functions of embodimentsof the present invention.

The immobilizing device 100 of FIGS. 5A-5C is configured to surround avehicle wheel 12 without being physically attached thereto. Theillustrated immobilizing device 100 includes an elongated frame 150having opposite end portions 150 a, 150 b. The frame 150 is movablebetween a first configuration (FIG. 5B) and a second configuration (FIG.5C). In the first configuration illustrated in FIG. 5B, the frame 150 iselongated sufficiently to allow the immobilizing device 100 to beinstalled around a vehicle wheel 12. In the second configuration, theframe 150 is collapsed such that the immobilizing device 100 snuglysurrounds a vehicle wheel 12 and such that the immobilizing device 100cannot be removed therefrom.

The illustrated immobilizing device 100 includes a pair of opposing endwalls 152, each located at a respective end portion 150 a, 150 b of theframe 150. Each end wall 152 has an edge portion 152 a angled inwardly,as illustrated. As such, when the frame 150 is in the collapsedconfiguration of FIG. 5C, the edge portions 152 a prevent theimmobilizing device 100 from being removed from a wheel 12. In addition,each end wall 152 has a height such that a vehicle wheel 12 cannot beraised enough (e.g., by raising the vehicle via a vehicle jack) to beremoved from the immobilizing device 100.

The illustrated immobilizing device 100 also includes a restraining arm154 extending upwardly from the frame 150. The restraining arm 154 isconfigured to be in adjacent, closely spaced-apart relationship with avehicle wheel 12 and to prevent access to the wheel lug nuts. Bypreventing access to the lug nuts, the restraining arm 154 preventsremoval of a vehicle wheel from a vehicle. A lock 102 is configured tolock the frame 150 of the immobilizing device 100 in the collapsedconfiguration (FIG. 5C) and to lock the restraining arm 154 in place.

A user interface 108 is positioned below the restraining arm 14, asillustrated, and is configured to allow a user to interact with theimmobilizing device 100, as described above. The immobilizing device 100of FIGS. 5A-5C also includes a processor, 104 and memory 106, asdescribed above.

Referring to FIG. 6, a vehicle immobilizing device system 200 that canbe utilized, for example, by a parking authority, municipality, or otherthird party, is illustrated. The system 200 includes a plurality ofvehicle immobilizing devices (VIDs) 100 and a server 300 that isconfigured to wirelessly communicate with each of the immobilizingdevices 100 via a wireless communication network 400.

In some embodiments of the present invention, the server 300 isconfigured to generate an unlock code and an identification code for arespective immobilizing device 100 when the immobilizing device 100 isinstalled on a vehicle. The server 300 stores the generated unlock codeand identification code, and wirelessly transmits the unlock code to therespective immobilizing device processor 104 for storage in theimmobilizing device memory 106.

The server 300 may generate an unlock code and/or an identification codefor a respective vehicle immobilizing device 100 in various ways. Forexample, in some embodiments of the present invention, the server 300generates an unlock code and/or an identification code for a respectivevehicle immobilizing device 100 via a random number generator. Therandom number generator may be associated with the server 300, with theimmobilizing device 100, or may be associated with another devicegeographically remote from the server 300 that the server 300communicates with.

In other embodiments, an immobilizing device 100 (or the server 300)includes a clock 110 and the server 300 generates an unlock code and/oran identification code for the respective vehicle immobilizing deviceusing time and/or date information from the clock 110. In otherembodiments and as described above, a vehicle immobilizing device 100may include an environmental sensor 114 that is configured to obtainenvironmental condition information (e.g., temperature, humidity, windspeed, ozone levels, etc.) in a vicinity of the vehicle immobilizingdevice 100. The server 300 uses environmental condition informationobtained from the sensor 114 to generate an unlock code and/or anidentification code for the vehicle immobilizing device 100. In otherembodiments and as described above, a vehicle immobilizing device 100may include a GPS receiver 112. The server 300 uses location informationobtained from the GPS receiver 112 to generate an unlock code and/or anidentification code for the vehicle immobilizing device 100.

In some embodiments, one or more of the immobilizing devices 100 in thesystem 200 are configured to generate an unlock code and anidentification code at the time the immobilizing device 100 is installedon a vehicle, store the generated unlock code in memory 106, and thentransmit the unlock code and identification code to the server 300. Asdescribed above, a respective immobilizing device processor 104 maygenerate unlock codes in various ways. For example, in some embodiments,an immobilizing device 100 may include a clock 110 and the deviceprocessor 104 uses time and/or date information from the clock 110 togenerate an unlock code. In other embodiments, an immobilizing device100 may include an environmental sensor 114 that is configured to obtainenvironmental condition information in a vicinity of the immobilizingdevice 100. The device processor 104 uses environmental conditioninformation obtained from the sensor 114 to generate an unlock code. Inother embodiments, an immobilizing device 100 may include a GPS receiver112. The device processor 104 uses location information obtained fromthe GPS device 112 to generate an unlock code.

In some embodiments of the present invention, a mobile code generationdevice 500 may be utilized by an installer to generate an unlock codeand an identification code for an immobilizing device 100 when theimmobilizing device 100 is installed on a vehicle. The code generationdevice 500 may be a portable electronic device or may be an electronicdevice mounted within a vehicle of an installer. In some embodiments ofthe present invention, a code generation device 500 may be implementedvia a smart phone executing an application. The code generation device500 generates an unlock code and an identification code and wirelesslytransmits the generated unlock code and identification code to theserver 300 for storage. The code generation device 500 also transmitsthe unlock code to the respective immobilizing device processor 104 forstorage in the device memory 106.

The code generation device 500 may generate an unlock code and/or anidentification code for a respective vehicle immobilizing device 100 invarious ways. For example, in some embodiments of the present invention,the code generation device 500 generates an unlock code and/or anidentification code for a respective vehicle immobilizing device 100 viaa random number generator. The random number generator may be associatedwith the code generation device 500, with the server 300, with theimmobilizing device 100, or may be associated with another devicegeographically remote from the code generation device 500 that the codegeneration device 500 communicates with.

In other embodiments, an immobilizing device 100 includes a clock 110and the code generation device 500 generates an unlock code and/or anidentification code for a respective vehicle immobilizing device 100using time and/or date information from the clock 110. In otherembodiments, a vehicle immobilizing device 100 includes an environmentalsensor 114 that is configured to obtain environmental conditioninformation in a vicinity of the vehicle immobilizing device 100. Thecode generation device 500 uses environmental condition informationobtained from the sensor 114 to generate an unlock code and/or anidentification code for the vehicle immobilizing device 100. In otherembodiments, a vehicle immobilizing device 100 (or the code generationdevice 500) may include a GPS receiver 112. The code generation device500 uses location information obtained from the GPS receiver 112 togenerate an unlock code and/or an identification code for the vehicleimmobilizing device 100.

The system 200 of FIG. 6 may include a mixture of types of immobilizingdevices. For example, some immobilizing devices 100 may be conventionalwheel boot-type immobilizing devices (e.g., immobilizing device 100 ofFIG. 4A), and some immobilizing devices 100 may be configured toimmobilize a vehicle in other ways (e.g., immobilizing device 100 ofFIGS. 5A-5C). In addition, the system 200 may include a mixture ofimmobilizing devices 100 that can generate unlock codes andidentification codes and immobilizing devices 100 that cannot generateunlock codes and identification codes. In addition, some of theimmobilizing devices 100 in the system 200 may be configured to conductfinancial transactions, as described above, and some of the immobilizingdevices 100 may not be configured to conduct financial transactions.

In some embodiments of the present invention, a user may communicatewith the server 300 via a respective immobilizing device 100 and obtainadditional information. For example, a user may inquire about past duefines/debts, and may obtain information about what to do with animmobilizing device 100 when removed from a vehicle.

FIG. 7 illustrates an exemplary processor 104 and memory 106 of animmobilizing device 100, according to some embodiments of the presentinvention. The processor 104 communicates with the memory 106 via anaddress/data bus 130. The processor 104 may be, for example, acommercially available or custom microprocessor. The memory 106 isrepresentative of the overall hierarchy of memory devices containing thesoftware and data used to implement various functions of a vehicleimmobilizing device 100 as described herein. The memory 106 may include,but is not limited to, the following types of devices: cache, ROM, PROM,EPROM, EEPROM, flash, SRAM, and DRAM.

As shown in FIG. 7, the memory 106 may hold various categories ofsoftware and data: an operating system 132, a latch control module 134,an unlock code generation module 136, and unlock code matching module138, a device removal authorization module 140, and a financial paymentmodule 142. It is understood that an immobilizing device 100 accordingto embodiments of the present invention may not have all of thefunctionality illustrated in FIG. 7. For example, an immobilizing devicein accordance with some embodiments of the present invention may not beconfigured to handle financial transactions and, accordingly, may nothave a financial payment module 142.

The operating system 132 controls operations of a vehicle immobilizingdevice 100. In particular, the operating system 406 may manage theresources of a vehicle immobilizing device 100 and may coordinateexecution of various programs (e.g., the latch control module 134,unlock code generation module 136, unlock code matching module 138,device removal authorization module 140, financial payment module 142,etc.) by the processor 104.

The latch control module 134 comprises logic for causing the latchmechanism of an immobilizing device lock 102 to be moved between lockedand unlocked positions upon receipt of some authorization (e.g.,financial payment approval, etc.). The unlock code generation module 136comprises logic for generating an unlock code and an identification codefor an immobilizing device 100 (e.g., via a random number generator, viaa clock, via location information from a GPS receiver, via environmentalcondition information from an environmental sensor, etc.) at the time ofinstallation of the immobilizing device 100 on a vehicle. The unlockcode matching module 138 comprises logic for determining if an unlockcode input by a user via user interface 108, or received from a server300 (FIG. 6), matches an unlock code stored in memory 106. The deviceremoval authorization module 140 comprises logic for determining ifinformation input by a user via user interface 108, or received fromserver 300, is valid so as to allow removal of an immobilizing device100 from a vehicle. The financial payment module 142 comprises logic forreceiving financial payment information from a user, such as a vehicleowner, forwarding the financial payment information to a transactionapproval service, and receiving a response from the transaction approvalservice, e.g., either transaction approval or disapproval.

FIG. 8 illustrates an exemplary processor 104 and memory 106 of a server300 (FIG. 6), according to some embodiments of the present invention.The processor 304 communicates with the memory 306 via an address/databus 302. The processor 304 may be, for example, a commercially availableor custom microprocessor. The memory 306 is representative of theoverall hierarchy of memory devices containing the software and dataused to implement various functions of a server 300 as described herein.The memory 306 may include, but is not limited to, the following typesof devices: cache, ROM, PROM, EPROM, EEPROM, flash, SRAM, and DRAM.

As shown in FIG. 8, the memory 306 may hold various categories ofsoftware and data: an operating system 308, a vehicle immobilizingdevice (VID) communication module 310, an unlock code/identificationcode generation module 312, and a financial transaction module 314. Theoperating system 308 controls operations of a server 300. In particular,the operating system 308 may manage the resources of a server 300 andmay coordinate execution of various programs (e.g., vehicle immobilizingdevice (VID) communication module 310, unlock code/identification codegeneration module 312, financial transaction module 314, etc.) by theprocessor 304.

The VID communication module 310 comprises logic for communicating withimmobilizing devices 100 including transmitting data to immobilizingdevices 100 and receiving data from immobilizing devices 100. The unlockcode/identification code generation module 312 comprises logic forgenerating an unlock code and an identification code for an immobilizingdevice 100 at the time of installation of the immobilizing device 100 ona vehicle. The financial transaction module 314 comprises logic forreceiving financial payment information from a user, such as a vehicleowner, forwarding the financial payment information to a transactionapproval service, and receiving a response from the transaction approvalservice, e.g., either transaction approval or disapproval.

FIG. 9 illustrates an exemplary processor 504 and memory 506 of a codegeneration device 500 (FIG. 6), according to some embodiments of thepresent invention. The processor 504 communicates with the memory 506via an address/data bus 502. The processor 504 may be, for example, acommercially available or custom microprocessor. The memory 506 isrepresentative of the overall hierarchy of memory devices containing thesoftware and data used to implement various functions of a codegeneration device 500 as described herein. The memory 506 may include,but is not limited to, the following types of devices: cache, ROM, PROM,EPROM, EEPROM, flash, SRAM, and DRAM.

As shown in FIG. 9, the memory 506 may hold various categories ofsoftware and data: an operating system 508, a vehicle immobilizingdevice (VID)/server communication module 510, and an unlockcode/identification code generation module 512. In particular, theoperating system 508 may manage the resources of a code generationdevice 500 and may coordinate execution of various programs (e.g.,VID/server communication module 510, unlock code/identification codegeneration module 512, etc.) by the processor 504.

The VID/server communication module 510 comprises logic forcommunicating between the code generation device and the immobilizingdevices 100, and communicating between the code generation device andthe server 300. The unlock code/identification code generation module512 comprises logic for generating an unlock code and an identificationcode for an immobilizing device 100 at the time of installation of theimmobilizing device 100 on a vehicle.

Computer program code for carrying out operations of processors 104, 304and 504 discussed herein may be written in a high-level programminglanguage, such as Python, Java, AJAX (Asynchronous JavaScript), C,and/or C++, for development convenience. In addition, computer programcode for carrying out operations of exemplary embodiments of the presentinvention may also be written in other programming languages, such as,but not limited to, interpreted languages. Some modules may be writtenin assembly language or even micro-code to enhance performance and/ormemory usage. However, embodiments of the present invention are notlimited to a particular programming language. It will be furtherappreciated that the functionality of any or all of the program modulesmay also be implemented using discrete hardware components, one or moreapplication specific integrated circuits (ASICs), or a programmeddigital signal processor or microcontroller.

The foregoing is illustrative of the present invention and is not to beconstrued as limiting thereof. Although a few exemplary embodiments ofthis invention have been described, those skilled in the art willreadily appreciate that many modifications are possible in the exemplaryembodiments without materially departing from the novel teachings andadvantages of this invention. Accordingly, all such modifications areintended to be included within the scope of this invention as defined inthe claims. The invention is defined by the following claims, withequivalents of the claims to be included therein.

That which is claimed is:
 1. A vehicle immobilizing device configured toimpede vehicle motion, comprising: a lock having a latch mechanism thatis movable between locked and unlocked positions, wherein the latchmechanism locks the vehicle immobilizing device and preventsunauthorized removal of the vehicle immobilizing device from a vehicle;a user interface comprising a display; memory configured to store anunlock code; and a processor in communication with the user interfaceand memory, wherein the processor is configured to receive removalauthorization information input by a user via the user interface anddisplay the unlock code stored in the memory via the display in responseto receiving the removal authorization information, wherein theprocessor controls movement of the latch mechanism from the lockedposition to the unlocked position so that the vehicle immobilizingdevice can be removed from a vehicle in response to user entry of thedisplayed unlock code via the user interface.
 2. The vehicleimmobilizing device of claim 1, wherein the processor is configured toreceive an unlock code via the user interface and store the unlock codein memory.
 3. The vehicle immobilizing device of claim 1, wherein theuser interface comprises a touch screen display and/or a keypad.
 4. Thevehicle immobilizing device of claim 1, wherein the processor generatesan unlock code and stores the unlock code in the memory when the vehicleimmobilizing device is utilized to immobilize a vehicle.
 5. The vehicleimmobilizing device of claim 4, further comprising a clock, and whereinthe unlock code is generated using time and/or date information from theclock.
 6. The vehicle immobilizing device of claim 4, further comprisingan environmental sensor configured to obtain environmental conditioninformation in a vicinity of the vehicle immobilizing device, andwherein the unlock code is generated using environmental conditioninformation from the environmental sensor.
 7. The vehicle immobilizingdevice of claim 4, further comprising a Global Positioning System (GPS)receiver, and wherein the unlock code is generated using locationinformation from the GPS receiver.
 8. The vehicle immobilizing device ofclaim 1, further comprising a transceiver, and wherein the processor isconfigured to: receive financial payment information; report thefinancial payment information to a transaction approval service via thetransceiver; receive transaction approval or denial from the transactionapproval service via the transceiver; and display an unlock code storedin the memory via the display in response to receiving transactionapproval.
 9. The vehicle immobilizing device of claim 8, wherein theprocessor is configured to receive financial payment information inputvia the user interface.
 10. The vehicle immobilizing device of claim 8,further comprising a slot for receiving a payment card and a magneticstripe reader associated with the slot, and wherein the processor isconfigured to receive financial payment information from a magneticstripe of a payment card via the magnetic stripe reader.
 11. The vehicleimmobilizing device of claim 8, further comprising a near fieldcommunication (NFC) reader, and wherein the processor is configured toreceive payment information from an NFC tag in proximity with the nearfield communication reader.
 12. The vehicle immobilizing device of claim8, further comprising a radio-frequency identification (RFID) reader,and wherein the processor is configured to receive payment informationfrom an RFID tag in proximity with the RFID reader.
 13. The vehicleimmobilizing device of claim 1, wherein the vehicle immobilizing devicecomprises: a base; and a pair of clamping members extending from thebase, wherein the clamping members are movable relative to each otherfrom an open position wherein a vehicle wheel can be inserted betweenthe clamping members to a closed position wherein the clamping membersengage the vehicle wheel to prevent the vehicle immobilizing device frombeing removed from the vehicle wheel, and wherein the latch mechanismlocks the clamping members in the closed position.
 14. A vehicleimmobilizing device configured to impede vehicle motion, comprising: alock having a latch mechanism that is movable between locked andunlocked positions, wherein the latch mechanism locks the vehicleimmobilizing device and prevents unauthorized removal of the vehicleimmobilizing device from a vehicle; a user interface; memory configuredto store an unlock code; and a processor in communication with the userinterface and memory, wherein the processor is configured to receiveremoval authorization information input via the user interface and movethe latch mechanism from a locked position to an unlocked position sothat the vehicle immobilizing device can be removed from a vehicle,wherein the removal authorization information comprises financialpayment information and/or verification that payment has been made foran outstanding debt or fine.
 15. A method, comprising: immobilizing avehicle with an immobilizing device, wherein the immobilizing devicecomprises: a lock having a latch mechanism that is movable betweenlocked and unlocked positions; memory configured to store an unlockcode; and a processor in communication with the memory, wherein theprocessor controls movement of the latch mechanism from the lockedposition to the unlocked position; generating an unlock code and anidentification code for the vehicle immobilizing device via anelectronic device in wireless communication with the vehicleimmobilizing device processor; and storing the unlock code in thememory.
 16. The method of claim 15, further comprising wirelesslytransmitting the generated unlock code and identification code to aremote location for storage.
 17. A method of releasing a vehicleimmobilizing device from a vehicle, wherein the vehicle immobilizingdevice includes a lock having a latch mechanism that is movable betweenlocked and unlocked positions, a user interface, a memory having anunlock code stored therein, and a processor in communication with theuser interface and memory, and wherein the processor controls movementof the latch mechanism from the locked position to the unlockedposition, the method comprising: receiving removal authorizationinformation input via the user interface; and displaying an unlock codestored in the memory via the user interface in response to receiving theremoval authorization information.
 18. The method of claim 17, furthercomprising moving the latch mechanism from the locked position to theunlocked position in response to receiving user input of the unlock codevia the user interface.
 19. A vehicle immobilizing device configured toimpede vehicle motion, comprising: a lock that prevents unauthorizedremoval of the immobilizing device from a vehicle, wherein the lock isconfigured to receive and store an unlock code during installation ofthe immobilizing device on a vehicle, wherein the unlock code isgenerated by an electronic device external to the vehicle immobilizingdevice and that is in wireless communication with the vehicleimmobilizing device; and a user interface for providing the lock with anunlock code and for entering the unlock code to unlock the lock.
 20. Thevehicle immobilizing device of claim 19, wherein the user interfacecomprises a dial and/or a keypad.
 21. A method, comprising: immobilizinga vehicle with an immobilizing device, wherein the immobilizing devicecomprises a user interface and a lock that prevents unauthorized removalof the immobilizing device from the vehicle and that is configured toreceive and store an unlock code; generating an unlock code for thevehicle immobilizing device via an electronic device external to theimmobilizing device; and storing the unlock code in the lock via theuser interface.
 22. The method of claim 21, further generating anidentification code for the vehicle immobilizing device via theelectronic device and storing the identification code in the lock viathe user interface.
 23. The method of claim 22, further comprisingstoring the unlock code and identification code at a remote location viathe electronic device.